Method and apparatus for supporting bearer type for v2x communication in wireless communication system

ABSTRACT

A method and apparatus for receiving a bearer type indication for vehicle-to-everything (V2X) communication in a wireless communication system is provided. An eNodeB (eNB) with roadside unit (RSU) function transmits an indication of local gateway (L-GW) support for V2X communication to a mobility management entity (MME), receives a bearer type indication indicating that a specific bearer is for V2X communication from the MME, and performs an action according to the bearer type indication.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to wireless communications, and more particularly, to a method and apparatus for supporting a bearer type for vehicle-to-everything (V2X) communication in a wireless communication system.

Related Art

3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.

The pace of LTE network deployment is accelerating all over the world, which enables more and more advanced services and Internet applications making use of the inherent benefits of LTE, such as higher data rate, lower latency and enhanced coverage. Widely deployed LTE-based network provides the opportunity for the vehicle industry to realize the concept of ‘connected cars’. By providing a vehicle with an access to the LTE network, a vehicle can be connected to the Internet and other vehicles so that a broad range of existing or new services can be envisaged. Vehicle manufacturers and cellular network operators show strong interests in vehicle wireless communications for proximity safety services as well as commercial applications. LTE-based vehicle-to-everything (V2X) study is urgently desired from market requirement, and the market for vehicle-to-vehicle (V2V) communication in particular is time sensitive. There are many research projects and field tests of connected vehicles in some countries or regions, such as US/Europe/Japan/Korea.

V2X includes a vehicle-to-vehicle (V2V), covering LTE-based communication between vehicles, vehicle-to-pedestrian (V2P), covering LTE-based communication between a vehicle and a device carried by an individual (e.g. handheld terminal carried by a pedestrian, cyclist, driver or passenger), and vehicle-to-infrastructure/network (V2I), covering LTE-based communication between a vehicle and a roadside unit (RSU)/network. A RSU is a transportation infrastructure entity (e.g. an entity transmitting speed notifications) implemented in an eNodeB (eNB) or a stationary UE.

A local home network (LHN) means a set of (H)eNBs and local gateways (L-GWs) in the standalone GW architecture, where the (H)eNBs have Internet protocol (IP) connectivity for selected IP traffic offload (SIPTO) at the local network (SIPTO@LN) via all the L-GWs.

Local IP access (LIPA)/SIPTO architecture may be supported for V2X communication. In this case, an operation of cellular network node should be defined.

SUMMARY OF THE INVENTION

The present invention provides a method and apparatus for supporting a bearer type for vehicle-to-everything (V2X) communication in a wireless communication system. The present invention provides a method and apparatus for supporting local Internet protocol (IP) access (LIPA)/selected IP traffic offload (SIPTO) for V2X communication.

In an aspect, a method for receiving a bearer type indication for vehicle-to-everything (V2X) communication, by an eNodeB (eNB) with roadside unit (RSU) function, in a wireless communication system is provided. The method includes transmitting an indication of local gateway (L-GW) support for V2X communication to a mobility management entity (MME), receiving a bearer type indication indicating that a specific bearer is for V2X communication from the MME, and performing an action according to the bearer type indication.

In another aspect, an eNodeB (eNB) with roadside unit (RSU) function in a wireless communication system is provided. The eNB with RSU function includes a memory, and a processor, coupled to the memory, that transmits an indication of local gateway (L-GW) support for vehicle-to-everything (V2X) communication to a mobility management entity (MME), receives a bearer type indication indicating that a specific bearer is for V2X communication from the MME, and performs an action according to the bearer type indication.

V2X communication can be supported by LIPA/SIPTO architecture more efficiently.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows LTE system architecture.

FIG. 2 shows a block diagram of architecture of a typical E-UTRAN and a typical EPC.

FIG. 3 shows a block diagram of a user plane protocol stack of an LTE system.

FIG. 4 shows a block diagram of a control plane protocol stack of an LTE system.

FIG. 5 shows an example of a physical channel structure.

FIG. 6 shows an example of an architecture for V2X communication.

FIG. 7 shows an example of V2X communication based on LIPA/SIPTO architecture.

FIG. 8 shows a method for notifying an L-GW IP address for V2X communication or indication of L-GW support for V2X communication according to an embodiment of the present invention.

FIG. 9 shows a method for getting a correlation ID information for V2X communication according to an embodiment of the present invention.

FIG. 10 shows a method for identifying V2X data packets according to an embodiment of the present invention.

FIG. 11 shows a method for receiving a bearer type indication for V2X communication by eNB with RSU function according to an embodiment of the present invention.

FIG. 12 shows a communication system to implement an embodiment of the present invention.

DESCRIPTION OF EXEMPLARY EMBODIMENTS

The technology described below can be used in various wireless communication systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. The CDMA can be implemented with a radio technology such as universal terrestrial radio access (UTRA) or CDMA-2000. The TDMA can be implemented with a radio technology such as global system for mobile communications (GSM)/general packet ratio service (GPRS)/enhanced data rate for GSM evolution (EDGE). The OFDMA can be implemented with a radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), etc. IEEE 802.16m is an evolution of IEEE 802.16e, and provides backward compatibility with an IEEE 802.16-based system. The UTRA is a part of a universal mobile telecommunication system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of an evolved UMTS (E-UMTS) using the E-UTRA. The 3GPP LTE uses the OFDMA in downlink and uses the SC-FDMA in uplink. LTE-advance (LTE-A) is an evolution of the 3GPP LTE.

For clarity, the following description will focus on the LTE-A. However, technical features of the present invention are not limited thereto.

FIG. 1 shows LTE system architecture. The communication network is widely deployed to provide a variety of communication services such as voice over internet protocol (VoIP) through IMS and packet data.

Referring to FIG. 1, the LTE system architecture includes one or more user equipment (UE; 10), an evolved-UMTS terrestrial radio access network (E-UTRAN) and an evolved packet core (EPC). The UE 10 refers to a communication equipment carried by a user. The UE 10 may be fixed or mobile, and may be referred to as another terminology, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a wireless device, etc.

The E-UTRAN includes one or more evolved node-B (eNB) 20, and a plurality of UEs may be located in one cell. The eNB 20 provides an end point of a control plane and a user plane to the UE 10. The eNB 20 is generally a fixed station that communicates with the UE 10 and may be referred to as another terminology, such as a base station (BS), an access point, etc. One eNB 20 may be deployed per cell.

Hereinafter, a downlink (DL) denotes communication from the eNB 20 to the UE 10, and an uplink (UL) denotes communication from the UE 10 to the eNB 20. In the DL, a transmitter may be a part of the eNB 20, and a receiver may be a part of the UE 10. In the UL, the transmitter may be a part of the UE 10, and the receiver may be a part of the eNB 20.

The EPC includes a mobility management entity (MME) and a serving gateway (S-GW). The MME/S-GW 30 may be positioned at the end of the network. For clarity, MME/S-GW 30 will be referred to herein simply as a “gateway,” but it is understood that this entity includes both the MME and S-GW. A packet data network (PDN) gateway (P-GW) may be connected to an external network.

The MME provides various functions including non-access stratum (NAS) signaling to eNBs 20, NAS signaling security, access stratum (AS) security control, inter core network (CN) node signaling for mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmission), tracking area list management (for UE in idle and active mode), packet data network (PDN) gateway (P-GW) and S-GW selection, MME selection for handovers with MME change, serving GPRS support node (SGSN) selection for handovers to 2G or 3G 3GPP access networks, roaming, authentication, bearer management functions including dedicated bearer establishment, support for public warning system (PWS) (which includes earthquake and tsunami warning system (ETWS) and commercial mobile alert system (CMAS)) message transmission. The S-GW host provides assorted functions including per-user based packet filtering (by e.g., deep packet inspection), lawful interception, UE Internet protocol (IP) address allocation, transport level packet marking in the DL, UL and DL service level charging, gating and rate enforcement, DL rate enforcement based on access point name aggregate maximum bit rate (APN-AMBR).

Interfaces for transmitting user traffic or control traffic may be used. The UE 10 is connected to the eNB 20 via a Uu interface. The eNBs 20 are connected to each other via an X2 interface. Neighboring eNBs may have a meshed network structure that has the X2 interface. A plurality of nodes may be connected between the eNB 20 and the gateway 30 via an S1 interface.

FIG. 2 shows a block diagram of architecture of a typical E-UTRAN and a typical EPC. Referring to FIG. 2, the eNB 20 may perform functions of selection for gateway 30, routing toward the gateway 30 during a radio resource control (RRC) activation, scheduling and transmitting of paging messages, scheduling and transmitting of broadcast channel (BCH) information, dynamic allocation of resources to the UEs 10 in both UL and DL, configuration and provisioning of eNB measurements, radio bearer control, radio admission control (RAC), and connection mobility control in LTE ACTIVE state. In the EPC, and as noted above, gateway 30 may perform functions of paging origination, LTE IDLE state management, ciphering of the user plane, SAE bearer control, and ciphering and integrity protection of NAS signaling.

FIG. 3 shows a block diagram of a user plane protocol stack of an LTE system. FIG. 4 shows a block diagram of a control plane protocol stack of an LTE system. Layers of a radio interface protocol between the UE and the E-UTRAN may be classified into a first layer (L1), a second layer (L2), and a third layer (L3) based on the lower three layers of the open system interconnection (OSI) model that is well-known in the communication system.

A physical (PHY) layer belongs to the L1. The PHY layer provides a higher layer with an information transfer service through a physical channel. The PHY layer is connected to a medium access control (MAC) layer, which is a higher layer of the PHY layer, through a transport channel. A physical channel is mapped to the transport channel. Data between the MAC layer and the PHY layer is transferred through the transport channel. Between different PHY layers, i.e., between a PHY layer of a transmission side and a PHY layer of a reception side, data is transferred via the physical channel.

A MAC layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer belong to the L2. The MAC layer provides services to the RLC layer, which is a higher layer of the MAC layer, via a logical channel. The MAC layer provides data transfer services on logical channels. The RLC layer supports the transmission of data with reliability. Meanwhile, a function of the RLC layer may be implemented with a functional block inside the MAC layer. In this case, the RLC layer may not exist. The PDCP layer provides a function of header compression function that reduces unnecessary control information such that data being transmitted by employing IP packets, such as IPv4 or IPv6, can be efficiently transmitted over a radio interface that has a relatively small bandwidth.

A radio resource control (RRC) layer belongs to the L3. The RLC layer is located at the lowest portion of the L3, and is only defined in the control plane. The RRC layer controls logical channels, transport channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers (RBs). The RB signifies a service provided the L2 for data transmission between the UE and E-UTRAN.

Referring to FIG. 3, the RLC and MAC layers (terminated in the eNB on the network side) may perform functions such as scheduling, automatic repeat request (ARQ), and hybrid ARQ (HARQ). The PDCP layer (terminated in the eNB on the network side) may perform the user plane functions such as header compression, integrity protection, and ciphering.

Referring to FIG. 4, the RLC and MAC layers (terminated in the eNB on the network side) may perform the same functions for the control plane. The RRC layer (terminated in the eNB on the network side) may perform functions such as broadcasting, paging, RRC connection management, RB control, mobility functions, and UE measurement reporting and controlling. The NAS control protocol (terminated in the MME of gateway on the network side) may perform functions such as a SAE bearer management, authentication, LTE IDLE mobility handling, paging origination in LTE IDLE, and security control for the signaling between the gateway and UE.

FIG. 5 shows an example of a physical channel structure. A physical channel transfers signaling and data between PHY layer of the UE and eNB with a radio resource. A physical channel consists of a plurality of subframes in time domain and a plurality of subcarriers in frequency domain. One subframe, which is 1 ms, consists of a plurality of symbols in the time domain. Specific symbol(s) of the subframe, such as the first symbol of the subframe, may be used for a physical downlink control channel (PDCCH). The PDCCH carries dynamic allocated resources, such as a physical resource block (PRB) and modulation and coding scheme (MCS).

A DL transport channel includes a broadcast channel (BCH) used for transmitting system information, a paging channel (PCH) used for paging a UE, a downlink shared channel (DL-SCH) used for transmitting user traffic or control signals, a multicast channel (MCH) used for multicast or broadcast service transmission. The DL-SCH supports HARQ, dynamic link adaptation by varying the modulation, coding and transmit power, and both dynamic and semi-static resource allocation. The DL-SCH also may enable broadcast in the entire cell and the use of beamforming.

A UL transport channel includes a random access channel (RACH) normally used for initial access to a cell, an uplink shared channel (UL-SCH) for transmitting user traffic or control signals, etc. The UL-SCH supports HARQ and dynamic link adaptation by varying the transmit power and potentially modulation and coding. The UL-SCH also may enable the use of beamforming.

The logical channels are classified into control channels for transferring control plane information and traffic channels for transferring user plane information, according to a type of transmitted information. That is, a set of logical channel types is defined for different data transfer services offered by the MAC layer.

The control channels are used for transfer of control plane information only. The control channels provided by the MAC layer include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH) and a dedicated control channel (DCCH). The BCCH is a downlink channel for broadcasting system control information. The PCCH is a downlink channel that transfers paging information and is used when the network does not know the location cell of a UE. The CCCH is used by UEs having no RRC connection with the network. The MCCH is a point-to-multipoint downlink channel used for transmitting multimedia broadcast multicast services (MBMS) control information from the network to a UE. The DCCH is a point-to-point bi-directional channel used by UEs having an RRC connection that transmits dedicated control information between a UE and the network.

Traffic channels are used for the transfer of user plane information only. The traffic channels provided by the MAC layer include a dedicated traffic channel (DTCH) and a multicast traffic channel (MTCH). The DTCH is a point-to-point channel, dedicated to one UE for the transfer of user information and can exist in both uplink and downlink. The MTCH is a point-to-multipoint downlink channel for transmitting traffic data from the network to the UE.

Uplink connections between logical channels and transport channels include the DCCH that can be mapped to the UL-SCH, the DTCH that can be mapped to the UL-SCH and the CCCH that can be mapped to the UL-SCH. Downlink connections between logical channels and transport channels include the BCCH that can be mapped to the BCH or DL-SCH, the PCCH that can be mapped to the PCH, the DCCH that can be mapped to the DL-SCH, and the DTCH that can be mapped to the DL-SCH, the MCCH that can be mapped to the MCH, and the MTCH that can be mapped to the MCH.

An RRC state indicates whether an RRC layer of the UE is logically connected to an RRC layer of the E-UTRAN. The RRC state may be divided into two different states such as an RRC idle state (RRC_IDLE) and an RRC connected state (RRC_CONNECTED). In RRC_IDLE, the UE may receive broadcasts of system information and paging information while the UE specifies a discontinuous reception (DRX) configured by NAS, and the UE has been allocated an identification (ID) which uniquely identifies the UE in a tracking area and may perform public land mobile network (PLMN) selection and cell re-selection. Also, in RRC_IDLE, no RRC context is stored in the eNB.

In RRC_CONNECTED, the UE has an E-UTRAN RRC connection and a context in the E-UTRAN, such that transmitting and/or receiving data to/from the eNB becomes possible. Also, the UE can report channel quality information and feedback information to the eNB. In RRC_CONNECTED, the E-UTRAN knows the cell to which the UE belongs. Therefore, the network can transmit and/or receive data to/from UE, the network can control mobility (handover and inter-radio access technologies (RAT) cell change order to GSM EDGE radio access network (GERAN) with network assisted cell change (NACC)) of the UE, and the network can perform cell measurements for a neighboring cell.

In RRC_IDLE, the UE specifies the paging DRX cycle. Specifically, the UE monitors a paging signal at a specific paging occasion of every UE specific paging DRX cycle. The paging occasion is a time interval during which a paging signal is transmitted. The UE has its own paging occasion. A paging message is transmitted over all cells belonging to the same tracking area. If the UE moves from one tracking area (TA) to another TA, the UE will send a tracking area update (TAU) message to the network to update its location.

Vehicle-to-everything (V2X) communication is described. V2X communication contains three different types, which are vehicle-to-vehicle (V2V) communications, vehicle-to-infrastructure (V2I) communications, and vehicle-to-pedestrian (V2P) communications. These three types of V2X can use “co-operative awareness” to provide more intelligent services for end-users. This means that transport entities, such as vehicles, roadside infrastructure, and pedestrians, can collect knowledge of their local environment (e.g. information received from other vehicles or sensor equipment in proximity) to process and share that knowledge in order to provide more intelligent services, such as cooperative collision warning or autonomous driving.

V2X service is a type of communication service that involves a transmitting or receiving UE using V2V application via 3GPP transport. Based on the other party involved in the communication, it can be further divided into V2V service, V2I service, V2P service, and vehicle-to-network (V2N) service. V2V service is a type of V2X service, where both parties of the communication are UEs using V2V application. V2I service is a type of V2X Service, where one party is a UE and the other party is a road side unit (RSU) both using V2I application. The RSU is an entity supporting V2I service that can transmit to, and receive from a UE using V2I application. RSU is implemented in an eNB or a stationary UE. V2P service is a type of V2X service, where both parties of the communication are UEs using V2P application. V2N service is a type of V2X Service, where one party is a UE and the other party is a serving entity, both using V2N applications and communicating with each other via LTE network entities.

For V2V, E-UTRAN allows such UEs that are in proximity of each other to exchange V2V-related information using E-UTRA(N) when permission, authorization and proximity criteria are fulfilled. The proximity criteria can be configured by the mobile network operator (MNO). However, UEs supporting V2V service can exchange such information when served by or not served by E-UTRAN which supports V2X Service. The UE supporting V2V applications transmits application layer information (e.g. about its location, dynamics, and attributes as part of the V2V service). The V2V payload must be flexible in order to accommodate different information contents, and the information can be transmitted periodically according to a configuration provided by the MNO. V2V is predominantly broadcast-based. V2V includes the exchange of V2V-related application information between distinct UEs directly and/or, due to the limited direct communication range of V2V, the exchange of V2V-related application information between distinct UEs via infrastructure supporting V2X service, e.g., RSU, application server, etc.

For V2I, the UE supporting V2I applications sends application layer information to RSU. RSU sends application layer information to a group of UEs or a UE supporting V2I applications. V2N is also introduced where one party is a UE and the other party is a serving entity, both supporting V2N applications and communicating with each other via LTE network.

For V2P, E-UTRAN allows such UEs that are in proximity of each other to exchange V2P-related information using E-UTRAN when permission, authorization and proximity criteria are fulfilled. The proximity criteria can be configured by the MNO. However, UEs supporting V2P service can exchange such information even when not served by E-UTRAN which supports V2X Service. The UE supporting V2P applications transmits application layer information. Such information can be broadcast by a vehicle with UE supporting V2X service (e.g., warning to pedestrian), and/or by a pedestrian with UE supporting V2X service (e.g., warning to vehicle). V2P includes the exchange of V2P-related application information between distinct UEs (one for vehicle and the other for pedestrian) directly and/or, due to the limited direct communication range of V2P, the exchange of V2P-related application information between distinct UEs via infrastructure supporting V2X service, e.g., RSU, application server, etc.

FIG. 6 shows an example of an architecture for V2X communication. Referring to FIG. 6, the existing node (i.e. eNB/MME) or new nodes may be deployed for supporting V2X communication. The interface between nodes may be S1/X2 interface or new interface. That is, the interface between eNB1 and eNB2 may be X2 interface or new interface. The interface between eNB1/eNB2 and MME1/MME2 may be S1 interface or new interface.

Further, there may be two types of UE for V2X communication, one of which is a vehicle UE and the other is the RSU UE. The vehicle UE may be like the generic UE. The RSU UE is a RSU which is implemented in the UE, and can relay or multicast or broadcast the traffic or safety information or other vehicle UEs. For V2X communication, vehicle UEs may be communicated with each other directly via PC5 interface. Alternatively, vehicle UEs may be communicated with each other indirectly via the network node. The network node may be one of an eNB, a new entity for V2X communication, a new gateway for V2X communication, a RSU, etc. The network node may not be the MME or S-GW. Alternatively, a vehicle UE may broadcast data, and the RSU UE may receive the broadcast data. The RSU and another vehicle UEs may be communicated with each other indirectly via the network node. The network node may be one of an eNB, a new entity for V2X communication, a new gateway for V2X communication, a RSU, etc. In this case, the network node may not be the MME or S-GW.

Local IP access (LIPA)/selected IP traffic offload (SIPTO) at the local network (SIPTO@LN) is described. The SIPTO@LN function enables an IP capable UE connected via a (H)eNB to access a defined IP network (e.g. the Internet) without the user plane traversing the mobile operator's network. The subscription data in the home subscriber server (HSS) are configured per user and per access point name (APN) to indicate to the MME if offload at the local network is allowed or not. SIPTO@LN can be achieved by selecting a L-GW function collocated with the (H)eNB or selecting stand-alone GWs (with S-GW and L-GW collocated) residing in the local network. In both cases the selected IP traffic is offloaded via the local network. If the MME detects a change in SIPTO permissions in the subscription data for a given subscriber for a given APN and the subscriber has already established a SIPTO@LN PDN connection to that APN, the MME shall release the SIPTO@LN PDN connection for that APN with “reactivation requested” cause.

For a SIPTO@LN PDN connection, the eNB sets up and maintains an S5 connection to the EPC. The SIPTO@LN PDN connection is released after a handover is performed, and the collocated L-GW in the source eNB triggers the release over the S5 interface.

In case of SIPTO@LN with collocated L-GW support, the eNB supports the following additional functions:

-   -   transfer of the collocated L-GW IP address of the eNB over         S1-MME to the EPC at every idle-active transition;     -   transfer of the collocated L-GW IP address of the eNB over         S1-MME to the EPC within every uplink NAS transport procedure;     -   support of basic P-GW functions in the collocated L-GW such as         support of the SGi interface corresponding to SIPTO@LN;     -   additional support of first packet sending, buffering of         subsequent packets, internal direct L-GW-eNB user path         management and in sequence packet delivery to the UE;     -   support of the necessary restricted set of S5 procedures         corresponding to the support of SIPTO@LN function;     -   notification to the EPC of the collocated L-GW uplink tunnel         endpoint ID(s) (TEID(s)) or generic routing encapsulation (GRE)         key(s) for the SIPTO@LN bearer(s) over S5 interface within the         restricted set of procedures to be forwarded over S1-MME and         further used by the eNB as “SIPTO correlation id” for         correlation purposes between the collocated L-GW and the eNB;     -   triggering SIPTO@LN PDN connection release by the collocated         L-GW after a handover is performed.

In case of SIPTO@LN with collocated L-GW support, the MME supports the following additional functions:

-   -   SIPTO@LN activation for the requested APN based on SIPTO         permissions in the subscription data and received collocated         L-GW IP address;     -   transfer of the “SIPTO correlation id” to the eNB via the         initial context setup procedure and E-UTRAN radio access bearer         (E-RAB) setup procedure;     -   release of the SIPTO@LN PDN connection of an idle-mode UE when         the UE moves away from the coverage area of the eNB.

FIG. 7 shows an example of V2X communication based on LIPA/SIPTO architecture. Referring to FIG. 7, an eNB supports RSU function, and has a collocated L-GW based on the LIPA/SIPTO architecture. The L-GW may be connected to a V2X server by interface. Or, L-GW may also be collocated with the V2X server.

When LIPA/SIPTO architecture supports V2X communication and the L-GW is collocated with the eNB supporting RSU function (or, V2X server), various procedures for supporting V2X communication more efficiently may be proposed.

(1) According to an embodiment of the present invention, the eNB with RSU function may notify the MME of the L-GW IP address for V2X communication or indication of L-GW support for V2X communication. In this case, a cell-specific procedure or a UE-specific procedure may be used.

For a cell specific procedure, the MME may obtain the L-GW IP address for V2X communication or indication of L-GW support for V2X communication through S1 setup request/response messages. More specifically, in order to notify the MME of the L-GW IP address for V2X communication or indication of L-GW support for V2X communication, the eNB may transmit a S1 setup request message to the MME. The S1 setup request message may include an L-GW support indication for V2X communication. The L-GW support indication for V2X communication may correspond to the L-GW IP address for V2X communication. The MME may give a response to the eNB by using S1 setup response message. The S1 setup request/response messages are merely examples, and other existing or new message may also be used for the same purpose. For example, eNB configuration update/response message may be used to notify the MME of the L-GW IP address for V2X communication or indication of L-GW support for V2X communication.

FIG. 8 shows a method for notifying an L-GW IP address for V2X communication or indication of L-GW support for V2X communication according to an embodiment of the present invention. This embodiment corresponds to the UE-specific procedure. In step S100, the eNB with RSU function transmits a message, which includes an L-GW IP address for V2X communication or indication of L-GW support for V2X communication, E-UTRAN cell global ID (ECGI), tracking area ID (TAI), etc., to the MME. The message may correspond to one of initial UE message (for transition from idle to connected), uplink NAS transport message (for new service request, etc.) or tracking area update (TAU) message (for TAU). Or, a new message may be defined for notifying of the L-GW IP address for V2X communication or indication of L-GW support for V2X communication.

(2) According to another embodiment of the present invention, the eNB with RSU function may get a correlation ID information for V2X communication from the MME.

FIG. 9 shows a method for getting a correlation ID information for V2X communication according to an embodiment of the present invention. In step S200, the MME transmits a message, which includes a correlation ID for V2X communication for supporting of V2X L-GW, to the eNB with RSU function. The message may correspond to one of E-RAB setup request message (for new service request) or initial context setup request message (for transition from idle to connected). Or, a new message may be defined for getting a correlation ID information for V2X communication.

(3) According to yet another embodiment of the present invention, the eNB with RSU function may identify V2X data packets received from V-UE.

FIG. 10 shows a method for identifying V2X data packets according to an embodiment of the present invention. In step S300, the MME transmits a message, which includes a bearer type indication, to the eNB with RSU function. The bearer type indication may indicate that a specific bearer is a bearer for V2X communication (i.e. V2I, V2V, V2P). The message may correspond to one of E-RAB setup request message (for new service request) or initial context setup request message (for transition from idle to connected). Or, a new message may be defined for getting a correlation ID information for V2X communication.

Upon receiving the bearer type indication, the eNB with RSU function, with which the L-GW collocated, may treat the specific bearer as a bearer for V2X communication, and take further action. For example, the eNB with RSU function may communicate with V2X server. Or, the eNB with RSU function may communicate with other neighbor eNBs. Or, the eNB with RSU function may switch the specific bearer from Uu interface (i.e. UE-to-network interface) to PC5 interface (i.e. UE-to-UE interface), or vice versa.

FIG. 11 shows a method for receiving a bearer type indication for V2X communication by eNB with RSU function according to an embodiment of the present invention. The embodiment shows in FIG. 8 to FIG. 10 may be applied to this embodiment. The eNB with RSU function may be collocated with L-GW. The V2X communication may include V2V communication, V2P communication and V2I communication.

In step S400, the eNB with RSU function transmits an indication of L-GW support for V2X communication to an MME. The indication of L-GW support for V2X communication may include an L-GW IP address for V2X communication. Further, the indication of L-GW support for V2X communication includes at least one of an ECGI, or a TAI. For UE-specific procedure, the indication of L-GW support for V2X communication may be transmitted via one of an initial UE message, an uplink NAS transport message or a TAU message. For cell-specific procedure, the indication of L-GW support for V2X communication may be transmitted via a S1 setup request message.

In step S410, the eNB with RSU function receives a bearer type indication indicating that a specific bearer is for V2X communication from the MME. The bearer type indication may be received via one of an E-RAB setup request message or an initial context setup request message. The bearer type indication may identify that V2X data packets received from a V-UE corresponds to the specific bearer for V2X communication.

Further, the eNB with RSU function may receive a correlation ID for V2X communication from the MME. The correlation ID for V2X communication may be received via one of an E-RAB setup request message or an initial context setup request message.

In step S420, the eNB with RSU function performs an action according to the bearer type indication. The action may include communicating with a V2X server, communicating with other neighboring eNBs, or switching V2X packets from Uu interface to PC5 interface, or vice versa.

FIG. 12 shows a communication system to implement an embodiment of the present invention.

An eNB with RSU function node 800 may include a processor 810, a memory 820 and a transceiver 830. The processor 810 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of the radio interface protocol may be implemented in the processor 810. The memory 820 is operatively coupled with the processor 810 and stores a variety of information to operate the processor 810. The transceiver 830 is operatively coupled with the processor 810, and transmits and/or receives a radio signal.

An MME 900 may include a processor 910, a memory 920 and a transceiver 930. The processor 910 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of the radio interface protocol may be implemented in the processor 910. The memory 920 is operatively coupled with the processor 910 and stores a variety of information to operate the processor 910. The transceiver 930 is operatively coupled with the processor 910, and transmits and/or receives a radio signal.

The processors 810, 910 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and/or data processing device. The memories 820, 920 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and/or other storage device. The transceivers 830, 930 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in memories 820, 920 and executed by processors 810, 910. The memories 820, 920 can be implemented within the processors 810, 910 or external to the processors 810, 910 in which case those can be communicatively coupled to the processors 810, 910 via various means as is known in the art.

In view of the exemplary systems described herein, methodologies that may be implemented in accordance with the disclosed subject matter have been described with reference to several flow diagrams. While for purposed of simplicity, the methodologies are shown and described as a series of steps or blocks, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the steps or blocks, as some steps may occur in different orders or concurrently with other steps from what is depicted and described herein. Moreover, one skilled in the art would understand that the steps illustrated in the flow diagram are not exclusive and other steps may be included or one or more of the steps in the example flow diagram may be deleted without affecting the scope and spirit of the present disclosure. 

What is claimed is:
 1. A method for receiving a bearer type indication for vehicle-to-everything (V2X) communication, by an eNodeB (eNB) with roadside unit (RSU) function, in a wireless communication system, the method comprising: transmitting an indication of local gateway (L-GW) support for V2X communication to a mobility management entity (MME); receiving a bearer type indication indicating that a specific bearer is for V2X communication from the MME; and performing an action according to the bearer type indication.
 2. The method of claim 1, wherein the bearer type indication is received via one of an E-UTRAN radio access bearer (E-RAB) setup request message or an initial context setup request message.
 3. The method of claim 1, wherein the bearer type indication identifies that V2X data packets received from a vehicle user equipment (V-UE) corresponds to the specific bearer for V2X communication.
 4. The method of claim 1, wherein the action includes communicating with a V2X server.
 5. The method of claim 1, wherein the action includes communicating with other neighboring eNBs.
 6. The method of claim 1, wherein the action includes switching V2X packets from Uu interface to PC5 interface, or vice versa.
 7. The method of claim 1, wherein the indication of L-GW support for V2X communication includes an L-GW Internet protocol (IP) address for V2X communication.
 8. The method of claim 1, wherein the indication of L-GW support for V2X communication includes at least one of an E-UTRAN cell global ID (ECGI), or a tracking area ID (TAI).
 9. The method of claim 1, wherein the indication of L-GW support for V2X communication is transmitted via one of an initial UE message, an uplink non-access stratum (NAS) transport message or a tracking area update (TAU) message.
 10. The method of claim 1, wherein the indication of L-GW support for V2X communication is transmitted via a S1 setup request message.
 11. The method of claim 1, further comprising receiving a correlation ID for V2X communication from the MME.
 12. The method of claim 11, wherein the correlation ID for V2X communication is received via one of an E-RAB setup request message or an initial context setup request message.
 13. The method of claim 11, wherein the V2X communication includes a vehicle-to-vehicle (V2V) communication, a vehicle-to-pedestrian (V2P) communication and a vehicle-to-infrastructure/network (V2I) communication.
 14. The method of claim 11, wherein the eNB with RSU function is collocated with a L-GW.
 15. An eNodeB (eNB) with roadside unit (RSU) function in a wireless communication system, the eNB with RSU function comprising: a memory; and a processor, coupled to the memory, that: transmits an indication of local gateway (L-GW) support for vehicle-to-everything (V2X) communication to a mobility management entity (MME), receives a bearer type indication indicating that a specific bearer is for V2X communication from the MME, and performs an action according to the bearer type indication. 